Use “etc.” consistently

diff --git a/src/doc/build-script.md b/src/doc/build-script.md
index feb98fc455f81d889e6bcee0d0222db722ddc7a9..49fddf8a557976a3ab54b74be9311a575b886da5 100644 (file)
--- a/src/doc/build-script.md
+++ b/src/doc/build-script.md
@@ -347,10 +347,10 @@ The [`gcc` crate](https://crates.io/crates/gcc) abstracts a range of build
 script requirements for C code:
 
 * It invokes the appropriate compiler (MSVC for windows, `gcc` for MinGW, `cc`
-  for Unix platforms, etc).
+  for Unix platforms, etc.).
 * It takes the `TARGET` variable into account by passing appropriate flags to
   the compiler being used.
-* Other environment variables, such as `OPT_LEVEL`, `DEBUG`, etc, are all
+* Other environment variables, such as `OPT_LEVEL`, `DEBUG`, etc., are all
   handled automatically.
 * The stdout output and `OUT_DIR` locations are also handled by the `gcc`
   library.

diff --git a/src/doc/crates-io.md b/src/doc/crates-io.md
index a21cb3fffde6ba90829a27816c34b943f3e15ebc..87a32862d3821147d71cba9491aa87f1037bf44a 100644 (file)
--- a/src/doc/crates-io.md
+++ b/src/doc/crates-io.md
@@ -209,7 +209,7 @@ to manage a crate.
 
 Occasions may arise where you publish a version of a crate that actually ends up
 being broken for one reason or another (syntax error, forgot to include a file,
-etc). For situations such as this, Cargo supports a “yank” of a version of a
+etc.). For situations such as this, Cargo supports a “yank” of a version of a
 crate.
 
 ```notrust

diff --git a/src/doc/pkgid-spec.md b/src/doc/pkgid-spec.md
index 30b736d692591eb76e6416360acfea9f81fc15f0..8b28d7d9fc879ed11c8b7d39e1a2129d9fa2a76f 100644 (file)
--- a/src/doc/pkgid-spec.md
+++ b/src/doc/pkgid-spec.md
@@ -3,7 +3,7 @@
 # Package ID Specifications
 
 Subcommands of cargo frequently need to refer to a particular package within a
-dependency graph for various operations like updating, cleaning, building etc.
+dependency graph for various operations like updating, cleaning, building, etc.
 To solve this problem, cargo supports Package ID Specifications. A specification
 is a string which is used to uniquely refer to one package within a graph of
 packages.